|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 22.2
|
|
Title:
|
MEF 22.2 Mobile Backhaul Phase 3 - Implementation Agreement
This document identifies the requirements for MEF Ethernet Services and MEF External Interfaces (EIs such as User-Network Interface (UNI)s) for use in Mobile Backhaul networks based on MEF specifications. In addition, new interface and service attributes have been specified where needed. The services and requirements in this Implementation Agreement (IA) are based on the services defined in MEF 6.2 [3], MEF 33[26] and MEF 51 [29] as well as the attributes in MEF 10.3 [7], MEF 26.1 [23] and this IA. The aim is to be flexible to support a wide range of Ethernet service based mobile network deployments.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2016
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet service definitions in MEF 22.2 supplement MEF 6.2 to form the basis of this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services in support of MBH.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
MEF 22.2 is an implementation agreement that applies and extends MEF 6.2 and MEF 10.3 for MBH
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
MEF Specifications/
[1] MEF 3, “Circuit Emulation Service Definitions, Framework and Requirements in Metro Ethernet Networks”/
[2] MEF 4, “Metro Ethernet Network Architecture Framework Part 1: Generic Framework”/
[3] MEF 6.2, “Ethernet Services Definitions - Phase 3”/
[4] MEF 8, “Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks”/
[5] MEF 9, “Abstract Test Suite for Ethernet Services at the UNI”/
[6] MEF 10.2, “Ethernet Services Attributes - Phase 2”/
[7] MEF 10.3, “Ethernet Services Attributes - Phase 3”/
[8] MEF 10.3.1, “Composite Performance Metric (CPM)”/
[9] MEF 10.3.2, “UNI Resiliency Enhancement”/
[10] MEF 11, “User Network Interface (UNI) Requirements and Framework”/
[11] MEF 12.2, “Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer”/
[12] MEF 13, “User Network Interface (UNI) Type 1 Implementation Agreement”/
[13] MEF 14, “Abstract Test Suite for Traffic Management Phase 1”/
[14] MEF 16, “Ethernet Local Management Interface”/
[15] MEF 17, “Service OAM Requirements & Framework”/
[16] MEF 19, “Abstract Test Suite for UNI Type 1”/
[17] MEF 20, “User Network Interface (UNI) Type 2 Implementation Agreement”/
[18] MEF 21, “Abstract Test Suite for UNI Type 2 Part 1 Link OAM”/
[19] MEF 22.1, “Mobile Backhaul Phase 2”/
[20] MEF 23.1, “Class of Service Phase 2 Implementation Agreement”/
[21] MEF 24, “Abstract Test Suite for UNI Type 2 Part 2 E-LMI”/
[22] MEF 25, “Abstract Test Suite for UNI Type 2 Part 3 Service OAM”/
[23] MEF 26.1, “External Network Network Interface (ENNI)–Phase 2”/
[24] MEF 27, “Abstract Test Suite for UNI Type 2 Part 5 - Enhanced UNI Attributes and Part 6 - L2CP Handling”/
[25] MEF 30.1, “Service OAM Fault Management Implementation Agreement”/
[26] MEF 33, “Ethernet Access Services Definition”/
[27] MEF 35.1, “Service OAM Performance Management Implementation Agreement”/
[28] MEF 45, “Multi-CEN L2CP”/
[29] MEF 51, “OVC Services Definitions”/
IEEE Specifications/
[30] IEEE Std. 802.1DTM-2004, “Part 3: Media Access Control (MAC) Bridges”/
[31] IEEE Std. 802.1QTM-2011, “Virtual Bridged Local Area Networks”/
[32] IEEE Std. 802.1AXTM-2014, “Link Aggregation”/
[33] IEEE Std. 802.3TM-2012, “Ethernet”/
[34] IEEE Std. 802.16TM-2009, “Air Interface for Fixed and Mobile Broadband Wireless Systems”/
[35] IEEE Std. 1588TM-2008, “Standard for A Precision Clock Synchronization Protocol for Network Measurement and Control Systems”/
ITU-T Recommendations/
[36] ITU-T Y.1541, “Network Performance Objectives For IP-Based Services”, April 2002/
[37] ITU-T Y.1563, “ETH transfer performance and availability performance”, January 2009/
[38] ITU-T G.8260, “Definitions and terminology for synchronization in packet networks”, August 2010/
[39] ITU-T G.8261/Y1361, Timing and Synchronization aspects in Packet Networks, April 2008/
[40] ITU-T G.8261.1/Y.1361.1 Packet delay variation network limits applicable to packet-based methods (Frequency synchronization), February 2012/
[41] ITU-T G.8262/Y.1362 Timing Characteristics of Synchronous Ethernet Equipment Slave Clock (EEC), July 2010/
[42] ITU-T G.8263/Y.1363 Timing characteristics of packet-based equipment clocks, February 2012/
[43] ITU-T G.8264/Y.1364 Distribution of timing through packet networks, May 2014/
[44] ITU-T G.8264/Y.1364 Amendment 1, January 2015/
[45] ITU-T G.8265/Y.1365, “Architecture and requirements for packet based frequency delivery”, October 2010/
[46] ITU-T G.8265.1, “IEEE1588(TM) profile for telecom (frequency delivery without support from network nodes)”, June 2010/
[47] ITU-T G.8275.1/Y.1369.1, “Precision time protocol telecom profile for phase/time synchronization with full timing support from the network”, July 2014/
[48] ITU-T G.703, “Physical/electrical characteristics of hierarchical digital interfaces”, November 2001/
[49] ITU-T G.781, “Synchronization layer functions”, September 2008/
[50] ITU-T G.803, “Architecture of transport networks based on the synchronous digital hierarchy (SDH)”, March 2000/
[51] ITU-T G.810, “Definitions and terminology for synchronization networks”, August 1996./
[52] ITU-T G.811, “Timing characteristics of primary reference clocks”, September 1997/
[53] ITU-T G.812, “Timing requirements of slave clocks suitable for use as node clocks in synchronization networks”, June 2004/
[54] ITU-T G.812, Erratum 1 (2004), March 2009/
[55] ITU-T G.813, “Timing characteristics of SDH equipment slave clocks (SEC)”, March 2003/
[56] ITU-T G.813, Corrigendum 1 (2003), June 2005/
[57] ITU-T G.823, “The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy”, March 2000/
[58] ITU-T G.824, “The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy”, March 2000/
[59] ITU-T G.825, “The control of jitter and wander within digital networks which are based on synchronous digital hierarchy (SDH)”, March 2000/
[60] ITU-T G.705, “Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks”, October 2005/
GSM & CDMA/
[61] GSM 01.04 v8, “Abbreviations and Acronyms”, May 2000/
[62] TIA IS-2000.1-A, “Physical Layer Standard for cdma2000 Spread Spectrum Systems”, March 2000/
[63] TIA/EIA-95-B, “Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems”, (ANSI/TIA/EIA-95-B-99) (reaffirmed to TIA-95-B), March 1999/
3GPP and 3GPP2 Technical Specifications/
[64] ETSI TS 145.010 v4.0.0.0, “GSM: Digital cellular telecommunication system (Phase 2+); Radio subsystem synchronisation (GSM 05.10)"/
[65] 3GPP2 C.S0002-E v2.0 (2010-06), “Physical Layer Signaling Standard for cdma2000 Spread Spectrum Systems”,/
[66] 3GPP2 C.S0010-C v2.0 (2006-03), “Recommended Minimum Performance Standards for cdma2000 Spread Spectrum Base Stations”/
[67] 3GPP TS 21.905V12.0.0 (2013-06), “Vocabulary for 3GPP Specifications”/
[68] 3GPP TS 22.278V12.6.0 (2014-12), “Service requirements for the Evolved Packet System (EPS)”/
[69] 3GPP TS 23.060v12.9.0 (2015-06), “General Packet Radio Service (GPRS); Service description; Stage 2”/
[70] 3GPP TS 23.107V12.0.0 (2014-09), “Quality of Service (QoS) concept and architecture”/
[71] 3GPP TS 23.203V12.9.0 (2015-06), “Technical Specification Group Services and System Aspects; Policy and charging control architecture”/
[72] 3GPP TS 23.236V12.0.0 (2013-06), Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes”/
[73] 3GPP TS 23.401V12.9.0 (2015-06), “Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access”/
[74] 3GPP TS 25.123V12.1.2 (2014-04), “Requirements for support of radio resource management (TDD)”/
[75] 3GPP TS 25.104V12.5.9 (2015-01), “ Base Station (BS) radio transmission and reception (FDD)”/
[76] 3GPP TS 25.105V12.1.0 (2015-01), “ Base Station (BS) radio transmission and reception (TDD)”/
[77] 3GPP TS 25.346.V12.0.0 (2014-03), “Introduction of the Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2”/
[78] 3GPP TS 25.402V12.1.0 (2014-12), “Synchronization in UTRAN Stage 2”/
[79] 3GPP TS 25.411V12.0.0 (2014-09), “UTRAN Iu interface layer 1”/
[80] 3GPP TR 25.866V9.0.0 (2010-01), “1.28Mcps TDD Home NodeB study item”/
[81] 3GPP TS 25.913V8.0.0, “Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)”/
[82] 3GPP TS 25.933V5.4.0 (2004-1), ”IP Transport in UTRAN”/
[83] 3GPP TS 36.104V12.7.0 (2015-03), ” Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception”/
[84] 3GPP TS36.133V12.7.0.0 (2015-04), “Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management”/
[85] 3GPP TS 36.300V12.5.0 (2015-03), “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2”/
[86] 3GPP TR36.401V12.2.0 (2015-03), ” Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description”/
[87] 3GPP TR 36.842 V12.0.0 (2014-01), “Technical Specification Group Radio Access Networks; Study on Small cell enhancements for E-UTRA and E-UTRAN”/
[88] 3GPP TR 36.922V12.0.0 (2014-10), “Evolved Universal Terrestrial Radio Access (E-UTRA); TDD Home eNode B (HeNB) Radio Frequency (RF) requirements analysis”/
Broadband Forum (BBF) Specifications/
[89] TR-221, " Technical Specifications for MPLS in Mobile Backhaul Networks" (October 2011)/
[90] TR-221 Amendment 1, " Technical Specifications for MPLS in Mobile Backhaul Networks" ( November 2013)/
IETF/
[91] RFC 791, “Internet Protocol”/
[92] RFC 1305, “Network Time Protocol (Version 3) – Specification, Implementation, and Analysis”/
[93] RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”/
[94] RFC 2460, “Internet Protocol, Version 6 (IPv6) Specification”/
[95] RFC 2474, “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers”/
[96] RFC 3386, “Network Hierarchy and Multilayer Survivability”/
[97] RFC 3550, “RTP: A Transport Protocol for Real-Time Applications”/
[98] RFC 4197, “Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks”/
[99] RFC 4301, “Security Architecture for the Internet Protocol”/
WiMAX Forum Specifications/
[100] WMF-T32-001-R016v01, “WiMAX Forum Network Architecture - Architecture Tenets, Reference Model and Reference Points Base Specification Stage 2. 2010-11-30”/
[101] WMF-T23-001-R015v02, “WiMAX Forum Mobile System Profile Specification, Release 1.5 Common Part, 2011-07-14”/
NGMN Alliance/
[102] NGMN Alliance, “NGMN Optimized Backhaul Requirements”, August 2008 (http://www.ngmn.org/uploads/media/NGMN_Optimised_Backhaul_Requirements.pdf)/
Small Cell Forum/
[103] Small Cell Forum 102.02.01, “Release two – Enterprise: Overview”, December 2013 CPRI/
[104] CPRI, “Common Public Radio Interface (CPRI); Interface Specification V6.0”, August 2013
|
|
9.
|
Qualification of
MEF:
|
|
|
The MEF was recognized under the provisions of ITU-T Recommendation A.5 on 24 September 2002. Qualifying information is on file with TSB.
9.5 The IPR policy of the MEF may be found in Article 10 of the MEF Bylaws which are available on the MEF public WEB site metroethernetforum.org.
9.6 All MEF Technical Specifications, Implementation Agreements, and Test Specifications are approved by an electronic letter ballot of all MEF members. For a MEF document to pass an electronic letter ballot at least a quorum of members (defined by the MEF bylaws as 1/3 of the MEF membership) must vote Yes or No. In addition, of the Yes plus No votes at least 75% of the votes must be Yes.
9.7 All published MEF documents are available for download free of charge in PDF or WORD format from the MEF public WEB site www.metroethernetforum.org .
9.8 Each revision of a given MEF document has a different MEF number.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
